This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
We are 100% certain the document exists and there are no Reader fields that would hide the document either. This problem occurs randomly for users and quite regularly for me as an Administrator.
Additionally, when we receive db links such as notes://server/replicaid it sometimes opens the wrong database!!
Our company has recently migrated to Outlook but we still use notes heavily and are using the Quest Coexistence tool. We originally thought this was related to Coexistence but we can duplicate the error by pasting the url into the Address Bar directly in notes.
After a few weeks of fighting this I believe the problem is with the way notes is processing the replica id portion of the url. It seems to be finding any db that matches the first few characters of the replica id instead of looking for an exact match. For instance, if I paste Notes://server/882575A00064B97D into the Address Bar it will find a db with the replica id of "882575A" and ignore the rest of it. (I haven't determined exactly how many characters it's using to locate the db.)
In this case, the "Document has been deleted" error makes sense because the document doesn't exist in the wrong db.
However, if I manually open the correct db beforehand, then paste the url into the address bar it will find the right document. That's because it knows which db to look for.
Therefore I believe the issue is how notes is processing the replica id portion of the url. What can we do to ensure it finds the exact match on the replicaid?
fyi: This affects both custom db's and standard notes templates so it's not a design issue.
Thank you
Feedback number WEBBANE243 created by ~Umberto Nonfanalitikle on 06/17/2017
Status: Open
Comments: